0.6.2

0.6.1

0.6.0

0.5.2

v15.9.0 (2024-06-21)

New Feature 🚀

• #4120 backport[v15]: Introduce "recommended" validation rules (@ benjie)

Bug Fix 🐞

• #3708 Fix crash in node when mixing sync/async resolvers (backport of #3706) (@ chrskrchr)
• #4000 Backport "Prevent Infinite Loop in OverlappingFieldsCanBeMergedRule" to v15 (@ benjie)

Internal 🏠

• #4126 backport(v15): fix publish scripts (@ benjie)

Committers: 2

• Benjie(@ benjie)
• Chris Karcher(@ chrskrchr)

• Add TS typings to the plugin (for better autocomplete), thanks @ belgattitude!
• Internal dependencies update

Chop chop! Next.js 12 yesterday, next-transpile-modules@9 today :] As always the breaking changes are indicated by the ⚠️ icon.

If you appreciate my work, and if you can afford it, you (or better, your company) can show support by sponsoring me (or just buying me a beer 🙌).

Support for Next.js 12

Nothing much to say. You should definitely upgrade, that's an amazing release!

Removed support for Webpack 4 ⚠️

What it says, next-transpile-modules is aligned with Next.js releases, so no more Webpack 4.

Removed support for legacy module resolution ⚠️

If you have seen in your logs with v8 the following warning:

DEPRECATED - fallbacking to previous module resolution system for module "XXX", you can now just pass the name of the package to transpile and it will detect its real path without you having to pass a sub-module.

this is for you.

You can read the 7.1.0 version changelog for a detailed explanation, but basically, what you want to do now is the following:

const withTM = require('next-transpile-modules')([
- 'some/very/specific/file.js'
+ 'some'
]);

• Update babel-relay-plugin to use graphql@0.8.2, which supports the latest revision of the GraphQL specification.
• Fix an issue with custom scalar field arguments not printing correctly.
• Promoted RelayGraphQLMutation to public API.
• Added rollback method to RelayGraphQLMutation.
• Added initial preparatory changes for moving to the new Relay API methods in a future release (eg. BabelPluginGraphQL).
• Avoid unnecessary un-ready updates.
• Add graphiqlPrinter argument to the RelayNetworkDebug constructor that can be used to print a link to view the request in GraphiQL.
• Fix problem using "node" as a key in a mutation response payload.

• Fix issue where containers would forget variables previously set with setVariables, specifically when using array/object variables (closes #1357).
• Add Relay.disableQueryCaching API (closes #754), which may be useful running Relay in a server context.
• Suppress spurious warning when using IGNORE as a rangeBehavior (closes #1337).
• Use a more accurate query name based on current route in RelayQuery.cloneWithRoute (see commit de954992), making logging and analytics that relies on query names more accurate.
• RelayNetworkDebug now prints an estimated request size (see commit b94ba409).
• Preserve type information in callsToGraphQL/callsFromGraphQL, fixing issues with null (closes #1256).
• Fix a subtle ordering issue by writing linked IDs before traversing plural linked fields; this solves a rare edge case where data could be written to the wrong ID given a recursive query (see commit be45692f).
• Expose injectCacheManager on RelayEnvironment (closes #1320).
• Expose Relay.QueryConfig (closes #1279).
• Ensure that instances of GraphQLRange get correctly deserialized (closes #1293).
• Fix a case where tracked nodes would incorrectly trigger a refetch of plural fields with null linked field children (see commit 5c08fd60).
• Make error-handling consistent between 200 status responses with errors attributes and non-200 responses (#1163).
• Warn when producing a diff query involving a client: ID, necessitating the use of a path when a refetchable ID would be preferable in order to produce a correct result (commit 928411df).

• Added a context property useFakeData that you can use to silence the warning when using a RelayContainer with fake data.
• You can now interpolate a function that returns an array of fragment references (eg. a route-conditional function) into a Relay.QL string. See #896
• Added RelayStoreData#toJSON.
• Fixed a bug where the query for a plural field might get diffed out, when in fact there was data missing in the store for which a query should have been produced.

• Added this.props.relay.pendingVariables which can be used to access variables from in-flight queries (to e.g. display a component-specific loading spinner).
• Examples are moving from their former home inside the main Relay repo into a separate relay-examples repository.
• npm run update-schema inside the Relay repo works again.
• Fix a potential race condition in GraphQLQueryRunner (only relevant to users of the non-public cache manager API).
• We now show line numbers in the Babel Relay plugin, making it easier to understand transform errors.
• Relaxed validation when using a rangeBehaviors function to allow non-string calls.
• subtractRelayQuery is removed.
• The printer now knows how to print Subscription nodes.
• RelayNetworkDebug is won't do anything unless console.groupCollapsed is available, because otherwise the output is too noisy to be useful.
• RelayContainer now uses more descriptive names for stateless functional components, instead of Relay(props => ReactElement).

• Relay is now built with Babel 6.
• Upgraded the Babel Relay plugin to graphql-js 0.6.0. Developers interested
  in upgrading to graphql-js 0.6.0 might have to make some changes to their
  existing GraphQL schemas. Read the migration guide for more information:
  https://gist.github.com/steveluscher/ffc1dfefbb10ad280c8a4c520a5c201c
• Debug information detailing every step of a Relay mutation is now printed to
  the console when DEV is true, and console.groupCollapsed and
  console.groupEnd are available.
• The this.props.relay prop passed into components by Relay.Container now
  exposes applyUpdate and commitUpdate methods for dispatching mutations
  in the context of the current Relay.Environment.
• RANGE_DELETE mutations can now remove multiple nodes from a connection,
  because deletedIDFieldName can now point to a plural field.
• You can now define rangeBehaviors as a function that receives the connection
  arguments and returns one of GraphQLMutatorConstants.RANGE_OPERATIONS.
• RelayNetworkDebug#init now lets you pass in a RelayEnvironment against
  which you would like to debug. This does not yet allow you to debug more than
  one environment at a time, but at least you can make the choice of which one.
• RelayReadyState now contains an events array; a stream of events that can
  be accessed from a RelayReadyStateCallback. You can reduce over this list of
  events to implement any kind of custom rendering logic you like.
• this.props.variables now reflects the variables after being processed with
  prepareVariables. The fact that variables were the un-prepared values was
  a source of confusion for many.
• Fixed a bug where prepareVariables could be called twice, breaking
  components with non-idempotent prepareVariables functions.
• Relay now warns when you try to set a variable using setVariables, or
  produce one through prepareVariables, that you have not declared in
  initialVariables upfront.
• It's now possible for the stale prop of a readyState to change even if
  there was previously an error present.
• Fixed a bug formatting error messages when the error being pointed to starts
  at column 0.
• A container definition can now optionally include a
  shouldComponentUpdate: () => boolean function. If specified, this function
  always overrides the default implementation (ie. there is no fall-through to
  the default).

• RelayNetworkDebug now logs query variables.
• RelayNetworkDebug is now added as a subscriber instead of replacing any
  existing network layers. It also no longer replaces the global fetch.
• Relay.Environment#injectNetworkLayer (and, by extension
  Relay#injectNetworkLayer) will now warn if injecting would overwrite a
  previously injected layer.
• Added experimental low-level RelayGraphQLMutation API (still being
  finalized and not yet documented, so use at your own risk).

• Added a React Native / Relay TodoMVC example app.
• You can now render multiple Relay apps at once, each with their own store.
  The following APIs are early versions and are as of yet undocumented so please
  use them with caution.
  • Added Relay.Environment. Relay.Store is now simply a global instance of
    RelayEnvironment. To create your own isolated store and network subsystem,
    create a new RelayEnvironment() and make use of it wherever environment
    is required.
  • Use Relay.Environment#injectNetworkLayer to inject a custom network layer
    for use within the context of a particular Relay.Environment instance.
  • Added Relay.ReadyStateRenderer. This component takes in an instance of
    Relay.Environment, a queryConfig that conforms to the
    RelayQueryConfigInterface, and a Relay container. It renders
    synchronously based on the supplied readyState. This primitive enables you
    to create alternatives to Relay.Renderer that fetch and handle data in a
    custom way (eg. for server rendered applications).
  • Added Relay.Renderer – a replacement for Relay.RootContainer that
    composes a Relay.ReadyStateRenderer and performs data fetching.
    Relay.RootContainer is now a wrapper around Relay.Renderer that
    substitutes Relay.Store for environment.
• Renamed the Flow type RelayRendererRenderCallback to RelayRenderCallback.
• Renamed the Flow type RelayQueryConfigSpec to RelayQueryConfigInterface.
• RelayContainer.setVariables will no longer check if the variables are
  changed before re-running the variables. To prevent extra work, check the
  current variables before calling setVariables.
• You can now roll back mutations in the COMMIT_QUEUED state using
  RelayMutationTransaction#rollback.
• When specifying a NODE_DELETE or RANGE_DELETE mutation config, you can
  omit parentID if your parent, in fact, does not have an ID.
• In cases where you query for a field, but that field is unset in the response,
  Relay will now write null into the store for that field. This allows you to
  return smaller payloads over the wire by simply omitting a key in the JSON
  response, rather than to write an explicit fieldName: null.
• If the relay prop does not change between renders, we now recycle the same
  object. This should enable you to make an efficient this.props.relay === nextProps.relay comparison in shouldComponentUpdate.
• You can now craft a connection query having invalid combinations of connection
  arguments (first/last/after/before) so long as the values of those arguments
  are variables and not concrete values (eg. friends(first: $first, last: $last) will no longer cause the Relay Babel plugin to throw).
• Added runtime validation to mutation configs to help developers to debug their
  Relay.Mutation.
• Added RelayNetworkDebug. Invoke
  require('RelayNetworkDebug').init(Relay.DefaultNetworkLayer) to enjoy simple
  to read logs of your network requests and responses on the console. Substitute
  your own network layer if you use one.
• Added two new rangeBehaviors:
  • IGNORE means the range should not be refetched at all.
  • REFETCH will refetch the entire connection.
• Connection diff optimization: Enables a mode where Relay skips diffing
  information about edges that have already been fetched. This can be enabled by
  adding @ relay(variables: ['variableNames']) to a connection fragment.

• The instance of Babel that the babel-relay-plugin receives will now be used when making assertions about version numbers.

• Identifying arguments on root fields can now be of any type - boolean, number, string, or array/object of the the same.
• Fixes a bug when we read connections or fragments without allocating a record until we encounter a child field that is not null. We now ensure that we allocate the record for connections and fragments (if it exists) regardless.
• Made babelAdapter compatible with Babel 6.6
• npm run build now works on Windows
• Tests now pass when using Node 5 / NPM 3
• Passing an empty array as a prop corresponding to a plural fragment no longer warns about mock data. The empty array is now passed through to the component as-is.
• Removed uri from RelayQueryConfigSpec. The uri property was part of RelayRoute, but never RelayQueryConfig. This revision simply cleans up the Flow shape in RelayContainer.
• RelayRenderer now runs queries after mount to make sure RelayRenderer does not run queries during synchronous server-side rendering.